Version 7.2 includes "secure cookies" for the authentication on Web Client and Mobile Web Client.
This can cause the login to fail and prevent users with valid credentials from logging-in!

Use one of these 2 Resolution options:
a. Fix by upgrading to latest macOS or Windows fw server app host OS.

b. OR fast local patch: Use the optional server.cfg's new variable "HTTPXMLAUTHMODE". The default value for this setting is "cookie" for the "secure cookie" support to be enabled. Exchange "cookie" with "key" to disable it, since it's not supported on the old host OS; change to this: "HTTPXMLAUTHMODE key".

If you have NOT used the optional "server.cfg" file before, download the below attached file called "serverhttpxmlauthmode-key.cfg". This file only contains this variable. All other available settings will get flushed into this file on the next fw server app launch.

• Quit the fw Server app.
• Rename the downloaded file to "server.cfg" and move it into the fw Server app's "system" folder.
• Launch your fw Server app and login to Web Client and Mobile Web Client.

In the main module bar > Projects (Advanced Project Search (APS)), for any filter including Bookings (Bookings, Project & Bookings), it is now possible to search by Involved Object and Involved Object Class.

You can list more than one Object inside square brackets [] to find Bookings that include any of them.

Additionally, in the Edit View of APS, you can now add new columns to display your search results:
• Involved Users
• Involved Non-Users
• Involved Object Classes
It's also possible to display selected classes and see who is involved from each class.

These enhancements allow users to more easily locate and display Bookings with specific involved resources.

In the Project module you can now save and load your searches. This will save:
1) Any filters that you searched by in the top search panel
2) The column widths
3) The column and direction of the sorting
4) Max hits

This can be done by clicking the "Save Search" button next to the "Filter From" or by going to the contect menu > Save Search.

To load a save you can go to the context menu > Load Search > select the saved search you want or click the "Load Search" button next to the "Save Search" button.

You can also delete saved search in context menu > Delete Search

When you load a search then that selection will be saved in the server (for everyone) and then loaded the next time you log in. Only the filters, column info, and sorting will be loaded at this point. To actually execute the search you will have to hit Enter or Search. The name of the saved search is also displayed next to Load and Save Search buttons.

It is now possible to update a custom field on multiple Projects by multi-selecting Projects in the main module bar "Projects" (Advanced Project Search) by using:
Filter From: Projects > right-click pop-up-menu > Edit Project Custom Field > select which Custom Field to edit from the list that is presented > type/select the needed value > OK.

Notes :

• The list of Custom Fields that are presented is a based on any Custom Field that farmerswife sees on any of the selected Projects, even if they come from different Project Custom Field Templates.
• If a Custom Field that is edited is not seen on one or more of the Selected Projects, nothing will be updated on those Projects.

Fixed a crash in the Advance Project Search when opening the popup menu

"APS" = Advanced Project Search = fw Client app > main module bar "Projects".

When you allocate a Group with Group Members to a Framework and save as Template and then re-apply to a marked time-range, the Group Members would wrongly not be booked.

This is now supported.

To enable this new Setting go to:
fw Client app > Toolbox > Booking Templates > sub-menu > "Check For Conflicts When Applying (Slow): No (default) / Yes".

This is a new Permission for Advanced Users: "Can Delete Bookings/Tasks"
When this is de-selected for a user they will receive a permissions error when trying to delete bookings or tasks.

The default value is True

This is a new Permission for Advanced Users: "Can Edit Bookings/Tasks"
When this is de-selected for a user they will receive a permissions error when trying to edit bookings or tasks.

The default value is True.

This is a new Permission for Advanced Users: "Can Edit Only Bookings/Tasks Status"
When this is selected for a user they can only edit/create/delete bookings with the selected status(es)

The default value is All, meaning that Bookings in All statuses can be edited.


✅ Users with Edit Permission Enabled & Matching Status: Can edit bookings only when the booking status matches the user’s assigned edit permission.
✅ Users with Edit Permission Enabled but Non-Matching Status:
Cannot edit bookings if the status does not align with their configured permissions, even though the edit right is generally enabled.
✅ Users with Edit Permission Disabled:
Are restricted from editing any bookings, regardless of booking status.

These permission updates ensure more precise access control aligned with organizational workflows, improving security and minimizing the risk of unintended changes.

With the newly added settings in the Server > Settings > Bookings:
1. Use Booking Check Point
2. Use Booking Fixed Price
it's possible to hide both options from the Booking Window in the Client Desktop App.

In fw Client app > Toolbox > Settings > Server Setup, there is now a setting called "Auto Delete After".
It has the options: Never (default), 14 Days, 30 Days, 90 Days; best-practice recommendation "30 Days".
If enabled, the Bookings in fw Client app > Toolbox > "Deleted Bookings And Binders" will be checked on a regular basis and "Bookings" will get purged if they were removed more than 14/30/90 days ago.

Previously the "Email Project Booking Report" sent from a particular
Booking would wrongly mention a different Booking in the email, and include the PDF Report with the same (wrong) Booking info.
Now the issue is fixed, and the Report is correctly sent from the selected Booking, including information from that Booking.

A new per-user setting: "Populate Detail Note From Object Note" available in the pop-up menu at the top of the Budget window.
If enabled, any Budget Details you add will have the Note field pre-populated with the current default Object Note.
This means it is possible to edit the Object Note for this particular budget line.

•It always takes the current value set in the Object Manager for that object.
•If you change the note inside the Budget, it will not update the Object’s note in the Object Manager.
•If you later edit the Object Note in the Object Manager, it won't update existing Budget Details.

In Summary, the Object Note is copied into the Budget Detail Note, and from there it can be edited individually without affecting the original Object Note.

There's a setting in fw Client app > Toolbox > Settings > Booking Defaults, called "Autofill Booking Name From First Object's Activity Or Class".
However the behavior it causes would not happen if you created a Booking from Scheduling Mode in a Budget.
Now we have added support for that behavior.

The automatic detection checks in this order:
(1) Check if the environment var exists: "TZ" with a valid IANA Timezone.
(2) Regional detection with offset, and
(3) Offset-only matching.

The standard one-time first check will add this new fw-Server-app-log-line like:
"Default Server TZ Name: Europe/Madrid"

After the first attempt to detect the local timezone of the host system, it can be overridden using a new "SERVERTZNAME" variable in server.cfg.

In fw Client app > Toolbox > Settings > Server Setup > Calendar Sync settings, users can create a Calendar Sync rule for Outlook Calendar and enable a new check-box “Use Delegated Authorization” in the Sync Rule settings to enable the OAuth2 Delegated authorization flow for users.
After enabling the check-box, it's important to select the fw user from the new button selector "Select A User" to clearly link the Sync Rule to a fw user.

Enter or confirm the Microsoft Tenant, Client ID, Secret and Redirect URI
and "Save" the settings.

Ensure the App Registration is using this Microsoft Graph > API Permission configuration:
Delegated:

• Calendars.ReadWrite
• User.Read (listed by default)

Go to: fw Client app > Toolbox > Settings > Server Setup > Calendar Sync > Setup > Settings > Notify Attendees: Yes (default) / No.

Once it’s on it will send an email to the involved user informing about the new event.

Added 2 new columns that can be added through "Edit View":

• Project / Cirkus Errors
• Booking / Cirkus Errors

In Cirkus, you can't time report on non-Users. So when it syncs the time reports back to farmerswife, it would previously always propagate the User's time report to all non-Users in the farmerswife Booking.

Now there's a setting to control this behavior: Toolbox > Settings > Cirkus > Propagate Cirkus Time Reports To Non-Users
The possible values are:

• No (Doesn't update the time reports of non-Users)
• Yes: Reported (Propagates the User's time report to the non-Users)
• Yes: Booked (Propagates the non-User object's booked time to its time report)

Cirkus won't allow modifications of Bookings in Closed Projects.
So now we skip syncing any Booking updates that happen after the Project is Closed, including Time Reports.

Cirkus won't allow modifications of Bookings that have been flagged as Invoiced.
So now we skip syncing any Booking updates that happen after the Booking is Invoiced.

Added support for importing Currency and Apply Tax values from Client csv import.

In the Server Setup > Contacts > Import Contacts you can now select to map to the cccurrency and ccapplytaxes fields. The cccurrency field expects a currency string that exists in the currency setup (should work with multiple currencies too) and the ccapplytaxes expects either YES or NO

In the Advanced Contact Search (fw Client app > main module bar "Contacts") you can now bulk edit some fields.

Supported fields:

• Custom Fields
• Currency
• Print Template
• Apply Tax
• Payment Terms
• Invoice Email Template
• Discounts

Previously the Edit windows within Dashboards didn't have a Cancel button.
Both the Edit Dashboard, and Edit Graph windows now have a Cancel button.

When selecting an Invoice Graph dashboard, clicking "Add Project" opens the Project-selection window.

From there you can:

• Select Projects using multi-selection:
• Drag-select with the mouse
• Shift-click to select a range
• Cmd (Mac) / Ctrl (Windows)-click to pick multiple individual Projects
• Remove selected Projects by clicking the trash/bin icon.

Users can now manage views within the Dispatch Tab with the following options:

1. Edit Views
• Show or hide specific columns
• Reorder columns via drag-and-drop
2. Save Views and Load from Saved Views
• Save customized layouts for quick reuse
3. Remove Views
• Delete saved views that are no longer needed

This bug was in the Dispatch module within the fw Client desktop app. When checking in an Item, switching to the Object Custom Field wrongly sent you back up the list.

This meant if you were adding e.g. an internal inventory number for a specific Object, then switching to fill in the number the UI would send you back to the top and you would lose the position you were working on.

Now the fixed behaviour will keep your place in the Dispatch so you can fill in the fields for your Objects.

Previously it was possible to create an Ad-hoc Check Out / Check In on closed (inactive) Projects.

The behaviour has now changed and inactive Projects do not appear on the list of Projects to choose from when creating new Check Out / Check In.

We implemented a new Dispatch History which gives you a clear record of changes made within a Dispatch.

•Creation of Check Out or Check In actions are tracked with the correct naming.

•Adding Objects, Media Order Numbers, Media Numbers, or Objects by Number is logged.

•Status changes (Ready / Verified or Unverified) are now reflected in the Dispatch History.

•All Dispatch changes are visible in the Dispatch History and also appear in the related Booking History.

•Project History remains unchanged and continues to only display the Booking entry with its link.

•Ability to export into a CSV file.

This functionality is useful to sort items in the desired order for Reports.

See more info here:
https://support.farmerswife.com/en/support/solutions/articles/17000089030-3-1-the-new-check-out-in-window

Added new “Add Object” and “Replace With Class Member” in the popup.

Added additional performance improvements and speed optimizations for large datasets.

And added a new data processing options located in fw Client app > main module bar "Dispatch" > left sub-menu > Settings >
“Search Items When Searching All (Can Be Slower) Yes / No (default)”.

By default, "Search All" no longer includes items, improving performance.
Users who are accustomed to searching items can re-enable this option if needed.

When you group by Invoice, the Header section automatically contains a field group called "From First Invoice". This is an old feature.
Now the same feature has also been added, but for Projects and Budgets.
So when grouping by Project, "From First Project" is available, and "From First Budget" when grouping by Budget.

When saving a Framework Booking (with an assigned Activity) as a Booking Template and re-applying it from the fw Client app's Toolbox, the Activity was wrongly not retained and instead reverted back to the Default Activity.

Re-applying a Booking Template now correctly preserves the assigned Activity from the original Framework Booking.

Changed for the Entry widget and Finder pop-up to now have "top anchor" position selection:
Changed so when focus is received, it marks the current text.
When the Finder info pops-up, now it does not select the first element in the list making typing with enter and not choosing easier.

https://support.farmerswife.com/support/solutions/articles/17000076036-view-port-select-time-frame#zofo

In the Hourline when you drag a Booking to the side and onto the trash-basket icon, you can choose to Delete an Object on a specific day, all Objects for a specific day or the entire Booking. This was broken and when confirming deleting, wrongly the entire Booking was deleted.

This bug is fixed now and the delete booking menu to choose what to delete is back.

The "Totals" calculations are now cached and other various speed-ups are implemented.
Search result no longer needs the Invoice lines to be fetched, significantly improving the performance when searching.

Previously it was only possible to add an Invoice Report as the default choice for an Invoice Template.

With this addition, you are now able to set a Financial Report as your default template for an invoice, so long as the Financial Report has the "For Invoicing" setting selected.

The "smarter" Long Form > "View Port" navigation improvements are located in the top right corner of the Long Form View Port area, where there are now 2 blue navigation arrow icons and a "Home" icon button for you to use them like this:

• Now you can extend (+1 week) the visible date range in the Long Form > View Port by holding the "Shift" key while navigating using the new "left"/"right" blue arrow buttons.

• Now you can combine multiple months in the View Port by 1st holding "Shift" key and only then clicking on the View Port > option-selector pop-up and then selecting one or more month from the month list.

• Now you can jump to the current month or fully reset the View Port mode by using the "Home" icon button.

• Use "Home + Shift" for the new "Hold Shift For Auto" feature to show you the "centered view" of all items loaded into the Long Form trees, to provide a "auto" view on the timeline.

When Running a Financial Report (FRD) from the Long Form > Objects pop-up, farmerswife now offers to select all days in view or month etc. based on the selection or not and if a Month is viable.
And in “LF Viewport” and in “dual calendar” you can now select the whole year.

In fw Client app > Toolbox > Media Orders there is now the option to Archive Selected Media Orders on "Done" and "Invoiced" Media Orders.

Previously it was only possible to archive Invoiced Media Orders.

Read this article for more information on Archiving: https://support.farmerswife.com/support/solutions/articles/17000025964-archiving-media-orders

The error stack trace contained this info:
element 13 missing from sublist "-1"

This bug is fixed.

Changed Multiple Currencies behaviour when raising a PO from Objects in Bookings to ignore Multiple Currencies settings from the Project, but instead to use the defaults and selected Division.

Added "Groupings" as separators that can be expanded/collapsed to the Object Tree.
Click the "Gear" icon > View > New Grouping to add a new grouping. Make a selection of Objects and when draggin and droping object to the objects tree oyu can drag them into that new grouping; allowing better organization of objects and resources.
These Groupings can be used to visually structure objects into logical sections.

• Added the Object Chooser ("+" icon) to the Objects tree's "Show Second Window".
• The Object Chooser now supports adding Projects directly into the Objects tree.
• Improved performance and responsiveness when working with large databases.
• Ongoing optimizations to speed up Object tree interactions.

Added "Projects Following Viewport" option:
• When enabled, the Objects tree automatically displays only Projects that contain Bookings or assigned Objects within the current Viewport date-range.
• As the Viewport date-range changes, the displayed Projects update automatically to match the visible period.

To enable:
Click the eye icon in Objects tree > Projects (Following View Port)

To enable this new "Second Objects Tree Bottom Window" go to fw Client app > Toolbox > Settings > Objects Tree > "Show Second Window".

Added the ability to export the Object Tree timeline as a PDF, enabling easier sharing and offline review of schedules.

Requires:
In fw Client app > Toolbox > Settings > Object Tree >
Classic Mode: No

Go to: fw Client app > Long Form > Objects tree and load a view of Objects or Projects into the Tree.

Next click on the new "gear icon" > "Save As PDF...".

A PDF output will be generated showing the information of the displayed view in the Object Tree.

Further examples and settings to configure the view can be found in this solution article: https://support.farmerswife.com/en/support/solutions/articles/17000149434-long-form-schedule-print

When a user timereports oOertime in fw Client app or in the Web Client, if their setting in "Web Profile Manager > Allow Editing Timereport > Send Email Notification When Reporting Overtime" is on, then they will be added to the Daily Overtime Report that is sent at the time of day specified in Toolbox Settings > Web Share Settings > Time Of Day To Send Overtime Timereport Email Notification.

This notification will be sent to users with the Permission Profile > Advanced Module > Receive Email Notification On Users Reporting Overtime.

Also you need to turn off the Setting in fw Client app > Toolbox Settings > Notifications > Silence All Notifications.

The Object Selector/Chooser can be accessed from various windows.
e.g. from Booking Window > Involved

The window is now bigger.
Added Column “available” that will show in some places depending on context call.
Added a class fast picker to load members from a class.
Added search selector for “Dispatch Location”.
Reordered the columns.
Added info text in top of window showing amount of results as well of date range and class if context.
Other minor changes.

New Object Manager columns that can be used in Object Manager Menu > Edit View:

• Tax
• Causes Conflict
• Force Unit Name
• Force Units Name

Previously if an object was activated or deactivated, the Object History would only note "Active" against the time stamp.

With this change, the Object History will now state "Activated" or "Deactivated" based on the action taken with the Object.

Requires in fw Client app > Toolbox > Settings > Objects Tree > "Classic Mode:" No / not checked.

Then see below the 4 new settings:
1) "Line Height" with multiple options.
2) "Crop Text" with options "Start", "Middle" and "End".

3) "Booking Text Line 1 (When Object)"
4) "Booking Text Line 2 (When Object)"

Options to Select to show for above 3) & 4):

• Client Name
• Project Name
• Binder Name
• Booking Name

You can now display Binders when showing Projects in the new Objects tree.

In fw Client app > Toolbox > Settings > Object Tree > IF "Classic Mode" is OFF there are these new Settings:

"Draw Binders Instead Of Bookings (Project)"

• Draw Sub Binders
• Draw Binder Content Text

You can now add Projects into the Long Form > Objects tree and it will show a single line for the Project with all its Bookings using the new "stacking" mode, which gives a really nice overview.

You can now slide / drag drop / extend / shorten (use shift key for trim) the Bookings in the (new) Objects tree mode.
Requires in fw Client app > Toolbox > Settings > Objects Tree > "Classic Mode: No / not checked"

If you hold shift key or control key you’ll get “Add” instead of view into list, when selecting Projects in Toolbox > Projects.

Previously, there wasn't a Permission to restrict users from deleting Projects.
Now there is this new permission "Can Delete Projects: Yes (default) / No".
It's enabled by default, to keep the previous behaviour intact.
And if set to "No" it will prevent users from deleting Projects, because the "Delete" option for Projects will be "greyed out" and is not usable.

New in fw Client app > Object Manager > Modify User window > Permissions > "Force Settings From User:".

The "Settings" is the configuration of ALL fw Client app > Toolbox > Settings of the selected user.

This new Feature is intended to replace the legacy "Force Settings From File".

When enabled the Users will no longer have access to Toolbox > Settings.

When a booking was created by selected the Time Range on the Longorm or Hourline, and then dragging & dropping the object on the time range, the "Set All Day As Default" setting was not respected.

Now this issue is fixed and the setting applies correctly.

Added new "Preview Pages" feature to all Print Designers, located in the top left corner to the right of the "Template" section.

The "Preview" is by default set to "5 Pages" and the new options are marked in yellow "attention" color.

The "Preview" options are:

• All Pages
• 3 Pages
• 5 Pages
• 10 Pages

Project History provides a detailed record of changes made within a Project.
To access it go to the Edit Project window > "View Settings / Options" "eye" icon menu > Show > History.

•Tracks new Bookings, Tasks, Virtual Bookings, Work Orders, Budgets, Binders, Extras, Services, and standard field changes (such as Owner, Project Type, or Custom Fields and more).

•Shows when a Booking is converted into a Task, including links to the updated Task or its new Project if reassigned.

•Virtual Bookings are logged when created, forwarded, or deleted, although they do not include a direct link.

•Only changes from new Projects and Bookings are recorded; past projects are not retroactively logged.

•Ability to export into a CSV file by using "Open As Spreadsheet".

Before certain Projects with Budget Operators on the Budget, would take 30+ seconds to open. This fix resolves the issue and the Project opens again within a second.

Added a new Setting in fw Client app > Toolbox > Settings > Projects Tree" called "Show Out Of View Bookings”.

This enables a new filtering for "out of view Bookings" in the Projects Tree that will speed up browsing in the Long Form > Projects tree and give better visibility on Bookings happening in the viewed Timeframe of the View Port.

Bookings out of the visible time frame will be indicated with a row in the Projects tree "x Earlier Out Of View Bookings Hidden".

If you click on it, the Bookings will be listed (though you have to navigate to the right time frame to see them in the View Port.

When the “Add Selected Projects To List" option was enabled, Projects dragged and dropped into the Project tree were incorrectly replacing already loaded Projects, instead of being added.
This behavior has now been fixed — dragged Projects are properly added to the list as expected.

Previously, the setting in Toolbox > Miscellaneous > Always Expand > Binders would not expand parent binders, yet Always Expand > Sub Binders was expanding them.

This fix corrects the behaviour so that Always Expand > Binders only expands Binders, and Always Expand > Sub Binders only expands Sub Binders.

In certain scenarios it could wrongly take 32 sec. to open a specific Project.
This issue is now fixed.

This new setting added in fw Client app > Toolbox > Settings > Server Setup: "Use REST API Cache: Yes / No (default)" currently:

• Only affects the REST API /event endpoint for fetching events.
• Support for caching other data-fetching endpoints will be added in the future for performance improvements.

• A full cache is created for all farmerswife events supported by the /event endpoint
• Optionally added activation for next fw Server app restart, avoiding delays during working hours.

• Now return 00:00 to 00:00 for "All-Day" events and for multiple-day events. Before some wrong times were delivered, like 06:00 or others depending on the "Day Start" configuration in fw Server > Setup.
• Example: If a Booking starts on 2025-01-01 at 08:00 and ends on 2025-01-04 at 15:00, the values for 2025-01-03 will now be 00:00 to 00:00 and for 2025-01-01 will be 08:00 to 00:00

• Booking-specific attributes (e.g. bookingLineCustoms) are now only visible for Project Booking events.

Break Time In and Break Time Out fields added in:
1) Object Report > Events
2) User Report > Events
3) Financial Report > Rows > Numbers

Contained error info: can't read "::TMPPDTEMPLATES": no such variable
Now Fixed.

To use this new feature go to: fw Server app > Setup > General > "DB Bulk Delete" button.

Included in the deletion operation:

• Bookings/Tasks with start date before selected date.
• Binders / Frameworks (and all Bookings within) with static date before the selected date.
• Personnel Events and Shifts before selected date.
• Dispatches with date before selected date.
• Maintenance before selected date.
• Requests before selected date.
• And their corresponding histories.

Previously, scheduling over-night Shifts was a bit tedious.
If the fw Server’s Day Start was set to 00:00, a Shift running from 21:00 to 05:00 had to be split into two separate Shifts due to the date-crossing. This also meant that such Shifts could not be included in a "Shift Pattern", since users can only be scheduled for one Shift per day. Splitting Shifts often caused unnecessary complexity — for example, requiring a user to appear as booked for two Shifts in one day.

With the new Setting in fw Client app Toolbox > Settings > Server Setup > "Allow Shifts Time Into Next Day: Yes / No (default)", you can now enable improved support for this.

Once enabled, the Shift window includes a new check-box: "Into Next Day".
Ticking this option allows you to schedule Shifts that cross over the Server’s configured Day Start (e.g., 21:00–05:00) no longer having to create two Shifts.

This improvement makes it easier to manage overnight Shifts and includes them seamlessly into Shift Patterns.

In Longform > Personnel Tree > Shift Type Setup > Edit Shift Patterns you can now define Shift Patterns to plot the selected Shift Types for a desired time frame. The shifts will be plotted for all members of the selected class. You can also define a Division for the shift pattern in which case you will only be able to select shift types of the selected division.

In the Settings Of the Shift Pattern you can configure the following:

• Rotation Pattern: Options are Weekly and Daily. This defines how the Shift Types are assigned to the members throughout the weeks. If Weekly is selected then members can only have the same Shift Type for the entire week.
• Required Shifts: Here you can add the required Shift Types. I.e. Shift Types that member should have at least 1 of for each week. In the Days column you can determine how many days per week you wan that shift to occur for each member.
• Weekends Off Per Month: Determines how many weekends per month each member should have off. By off here we mean weekends were for both days the member has a Required Shift.
• Minimum Hours Break: Determins the minimum hours each member should have between their shifts.
• Plot Over Personnel Events: Determines whether, when plotting shifts, it should ignore days where it has a personnel event.
• Plot Over Public Holidays: Determines whether it should plot shifts on days that are public holidays.

Shift Pattern Extension

The new Shift Pattern Extension functionality allows users to easily extend an existing shift pattern while maintaining its structure and rotation. This is designed to simplify long-term scheduling where recurring patterns continue beyond their initial end date.

When extending shift pattern:
• Both the original and the extended shift patterns become read-only, with the exception of the First Week Schedule, which remains editable.
• Users can also modify the name and end date of the extended pattern. The start date is fixed and automatically set as the day following the end of the original pattern.
• Only the most recently extended shift pattern can be extended further. Earlier patterns in the chain cannot be extended again.
• The shift rotation continues from where the previous pattern ended.
• If the Object Class membership has changed:

• Users removed from the class are greyed out in the First Week Schedule, but their shifts continue to rotate as before.
• Newly added users appear with empty rows in the First Week Schedule and can be assigned shifts manually.

Previously the data was cleared after the shift pattern has been applied and opened again. As a result it was not possible to see the First Week Schedule.

This is now supported and the First Week's Schedule of a shift pattern is saved.

The First Week Schedule got expanded, so the user can see all 7 days without scrolling (as long as the shift names are not too long).

Previously when editing shifts, users could select a shift from a different division, even if the setting “User can only book shifts from own Division” was enabled.

This behavior has now been corrected — the division restriction is properly enforced when replacing one shift with another.

In the Timeline > Utilisation Numbers, it's now possible to display utilisation numbers, based on:

Total Days (in the selected time period)
Total Hours (in the selected time period)
Hours Per Day
Hours Per Week

It's important to note that:

• Project and Task Bookings are counted only if they are Confirmed. If there is a conflict, the conflicting Booking is not included, unless it is Force Confirmed.
• Personnel Bookings marked as “All Day” are calculated as 24 hours.
• Shifts are excluded from all calculations.
• If a user or Object has multiple Bookings on the same day, they are counted as one booked day.

When in fw Client app > Long Form > Personnel tree, select e.g. a week in the View Port timeline.
You are now asked if you want to select the whole month (e.g. "Select September ?") before selecting the users.

Previously, when a user was upgraded from a Web User (WU) to an Advanced User (AU), their first login to the farmerswife Client desktop app would incorrectly display no navigation tabs in the main module bar and no tabs in the Toolbox.

This issue has now been fixed — newly upgraded Advanced Users will see all the required tabs correctly upon their first login.

When logging in with OpenID Connect, the "Force Settings From File" (*.wus) applied in the user's Permission Profile would wrongly not get applied.
The issue is fixed now.

Changed so when focus is received it marks the current text.
The Finder pop-up now does not select the first element in the list, making typing with enter and not choosing easier.

Previously when submitting a multiday “All Day” request in the iOS app that included a Daylight Saving Time (DST) transition date, the system duplicated the final day.

This is now fixed, preventing this from happening.